Clarify EZWallet Labs copy as claim-ticket QR flow - #134

Motivation

• The EZWallet UX was phrased like a traditional payment-request flow but the product is a Soroban-native claim/ticket model where the QR payload carries transfer/claim intent that recipients redeem, not a request for them to pay. This change aligns the UI copy with that intent.

Description

• Updated hero and subtitle copy in src/experiments/ezwallet/EZWalletApp.svelte to present EZWallet as a claim/value-ticket generator rather than a payment request.
• Renamed the builder section and option labels to 01 · Build Your Value Ticket QR and changed the mode options to Direct Claim Ticket and Event Ticket Drop in src/experiments/ezwallet/EZWalletApp.svelte.
• Clarified safety/review messaging to state the QR contains claim intent metadata and that redemption requires explicit signer approval in src/experiments/ezwallet/EZWalletApp.svelte.
• Updated the drop/redeem page heading and review notice to Stellar Claim Ticket and made the review copy explicit about claim intent in src/experiments/ezwallet/EZWalletDropApp.svelte.

Testing

• Ran TypeScript compile check with pnpm -s exec tsc --noEmit, which completed successfully.

Codex Task